Chassis cooling resource

ABSTRACT

Example implementations relate to a chassis cooling resource. In some examples, a chassis cooling resource includes a controller, comprising instructions to detect a failure corresponding to a first cooling system of a first chassis coupled to a server rack, and alter settings of a second cooling system of a second chassis coupled the server rack to provide additional cooling resources to the first cooling system in response to the detected failure.

BACKGROUND

A coolant distribution unit (CDU) can deliver conditioned liquid (e.g.,water) to a number of racks in a datacenter. The CDUs within adatacenter can operate with redundancy to ensure that if one or moreCDUs malfunction that additional CDUs can maintain cooling of the racks.A number of CDUs can each include an individual reservoir to containexcess liquid for utilizing with a cooling system coupled to the numberof CDUs. The conditioned liquid can be received at a number of serverracks that include a plurality of server chassis.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example controller for a chassis cooling resourceconsistent with the present disclosure.

FIG. 2 illustrates an example memory resource for a chassis coolingresource consistent with the present disclosure.

FIG. 3 illustrates an example system for a chassis cooling resourceconsistent with the present disclosure.

FIG. 4 illustrates an example system for a chassis cooling resourceconsistent with the present disclosure.

FIG. 5 illustrates an example system for a chassis cooling resourceconsistent with the present disclosure.

DETAILED DESCRIPTION

Coolant distribution units (CDUs) can utilize an enclosed loop todeliver conditioned liquid (e.g., water, coolant, etc.) to computingdevices within a server chassis and/or a server rack. In some examples,the CDU can deliver the conditioned liquid to cooling racks or liquid toliquid heat exchangers (e.g., rear door heat exchangers, etc.) that canbe coupled to a chassis of a server rack. In previous systems, theliquid to liquid heat exchanger in combination with a plurality of pumpscan deliver the liquid to a plurality of server chassis coupled to aserver rack.

In some examples, each of the server chassis can include a plurality ofserver blades that are independent from each of the other serverchassis. For example, a first server chassis can include a plurality ofserver blades that are monitored and controlled separately from a secondserver chassis. In some examples, the plurality of server chassis can bepowered independently. For example, a first server chassis can receiveelectrical power at a first connection of a power distribution unit(PDU) and a second server chassis can receive electrical power at asecond connection of the PDU. In some examples, a power failure of oneserver chassis may not affect other server chassis within the sameserver rack. In addition, other types of failures (e.g., controllerfailure, pump failure etc.) for one chassis may not affect a differentchassis coupled to the same server rack.

Systems described herein can be utilized to detect a failure of acooling system, a failure of a controller, a power failure, and/or afailure of a device that may affect the cooling system of a particularchassis coupled to a server rack. The systems described herein can beutilized to alter settings of a different chassis to provide additionalcooling resources to the particular chassis. Thus, the systems describedherein can be utilized as a failover system for cooling systems of aplurality of server chassis coupled to a server rack. For example, whena failure occurs at a first cooling system, a second cooling system canprovide cooling resources to the first cooling system. In otherexamples, the systems described herein can be utilized to determine ausage level (e.g., power usage level, usage state, etc.) of a firstserver chassis coupled to the server rack and alter settings of a secondserver chassis based on the determined usage level of the first serverchassis. In these examples, the second server chassis can providecooling resources to the first server chassis based on the determinedusage level.

The systems described herein can increase a pumping capacity andredundancy for each of the plurality of server chassis coupled to aserver rack. In addition, the systems described herein can provide anincrease in pumping and powering flexibility, which can be utilized toallocate cooling resources based on a usage of particular server chassiscoupled to the server rack. Furthermore, the systems described hereincan be utilized to support additional functionality (e.g., turbo mode,overclocking, etc.) of computing devices coupled to each of theplurality of server chassis by utilizing the increased pumping capacityof the system.

FIG. 1 illustrates an example controller 100 for a chassis coolingresource consistent with the present disclosure. The controller 100 mayperform a function related to chassis cooling resource. As illustratedin FIG. 1, the controller 100 may comprise a processing resource and amemory resource 102 storing machine-readable instructions to cause theprocessing resource to perform an operation relating to chassis coolingresource. In some examples, the controller 100 can be a chassiscontroller that is coupled to a particular server chassis and controlfunctions of the particular server chassis. For example, the controller100 can be utilized to monitor a functionality of a server chassisand/or perform functions relating to the cooling system of the serverchassis. In some examples, each server chassis coupled to a server rackcan include a corresponding chassis controller. In other examples, thecontroller 100 can be a controller for a plurality of server chassiscoupled to the server rack.

The controller 100 may include instructions 104 stored in the memoryresource 104 and executable by a processing resource to detect a failurecorresponding to a first cooling system of a first chassis coupled to aserver rack. In some examples, the controller 100 can determine that oneor more features of the first cooling system are non-functional ornon-responsive. For example, the detected failure can be a failure of apump coupled to the first chassis and/or the first cooling system. Inthis example, the pump failure can occur when a pump that is coupled tothe first chassis is non-functional, is performing below a thresholdlevel, and/or is not performing to manufacturer specifications. In someexamples, a pump failure can include an inability of the pump to keep upwith a particular demand. For example, the controller 100 can determinethat a power level of a first chassis is above a threshold for a pumpcoupled to the first chassis. In this example, it can be determined thatthe pump of the first chassis has failed or is not performing to amanufacturer specification.

In some examples, the detected failure can be a power failure of thefirst chassis that can affect the first cooling system. For example, thecontroller 100 can detect that a power failure has occurred with thefirst server chassis. In this example, the controller 100 can detect thepower failure based on a non-responsive heartbeat message from acontroller corresponding to the first server chassis. For example, thecontroller corresponding to the first chassis can send heartbeatmessages to the controller 100 during normal operation. In this example,the controller 100 may not receive a heartbeat message from thecontroller corresponding to the first chassis when there is a powerfailure. In another example, the controller 100 may not receive a signalfrom the controller corresponding to the first server chassis anddetermine that the controller corresponding to the first server chassishas failed or is not functioning to a manufacturer specification. Inthis example, the controller 100 can alter settings to provide resourcesto the first chassis and/or first cooling system of the first chassisbased on the detected failure.

The controller 100 may include instructions 106 stored in the memoryresource 104 and executable by a processing resource to alter settingsof a second cooling system of a second chassis coupled to the serverrack to provide additional cooling resources to the first cooling systemin response to the detected failure. In some examples, the controller100 can be communicatively coupled to the second chassis to altersettings of the second chassis and/or the second cooling system of thesecond chassis. For example, the controller 100 can be a chassiscontroller for the second chassis. In another example, the controller100 can be a controller for the server rack that includes the firstchassis and the second chassis.

In some examples, the instructions 106 can include instructions to altersettings of a pump coupled to the second chassis to provide additionalcooling resources to the first cooling system coupled to the firstchassis. For example, the first cooling system and the second coolingsystem can be coupled together by an auxiliary input manifold. In thisexample, the controller 100 can utilize the auxiliary input manifold andincrease a pump speed of a pump coupled to the second chassis to provideadditional cooling resources to the first cooling system via theauxiliary input manifold.

In some examples, the altered setting can include an increase in pumpspeed for a pump coupled to the second chassis to provide coolingresources to the first cooling system when a pump coupled to the firstchassis is inactivated due to a power failure of the first chassis. Forexample, the controller 100 can detect that a power failure has occurredat the first chassis. In this example, the controller 100 can activatean auxiliary power connection between the first chassis and the secondchassis to provide power to the first chassis. In this example, thecontroller 100 can also utilize an auxiliary input manifold to providecooling resources from the second cooling system to the first coolingsystem of the first chassis. In some examples, the controller 100 canprovide power to the pump coupled to the first chassis via the auxiliarypower connection when the first chassis loses power.

In some examples, the controller 100 can deactivate a controller of thefirst chassis and perform the functions of the controller of the firstchassis. For example, the controller 100 can be positioned within thesecond chassis and deactivate the controller within the first chassisand perform the functions of the controller positioned within the firstchassis as well as perform the functions corresponding to the secondchassis. In this way, the controller 100 can act as a back-up controllerfor the first chassis and add additional controller redundancy. Inanother example, the detected failure can include a chassis controllerof the first chassis losing controller signal. As used herein, acontroller signal can, for example, be a heartbeat message or other typeof signal that is utilized to determine when the chassis controller isfunctioning properly. In some examples, the controller 100 can determinethat the chassis controller of the first chassis is non-functional orhas failed and deactivate the chassis controller of the first chassis asdescribed herein.

The controller 100 can be utilized as a chassis controller for aspecific chassis (e.g., second chassis) or a central controller for aplurality of chassis coupled to the server rack. The controller 100 canbe utilized as a failover controller when there is a failure of achassis (e.g., chassis controller loses controller signal, chassis losespower, chassis cooling system fails, chassis pump fails, etc.). In someexamples, the controller 100 can be utilized to redistribute coolingresources from an active chassis cooling system to a failed chassiscooling system to provide a more redundant server rack.

FIG. 2 illustrates an example memory resource 210 for a chassis coolingresource consistent with the present disclosure. As used herein, amemory resource 210 can be a non-transitory machine-readable storagemedium. Although the following descriptions refer to an individualmemory resource 210, the descriptions may also apply to a system withmultiple processing resources and multiple machine-readable storagemediums. In such examples, the instructions may be distributed acrossmultiple machine-readable storage mediums and the instructions may bedistributed across multiple processing resources. Put another way, theinstructions may be stored across multiple machine-readable storagemediums and executed across multiple processing resources, such as in adistributed computing environment.

In some examples, the memory resource 210 can be coupled to a processingresource. A processing resource may be a central processing unit (CPU),microprocessor, and/or other hardware device suitable for retrieval andexecution of instructions stored in the memory resource 210. In someexamples, a processing resource may receive, determine, and sendinstructions 212, 214, 216, and 218. As an alternative or in addition toretrieving and executing instructions, a processing resource may includean electronic circuit comprising an electronic component for performingthe operations of the instructions in the memory resource 210. Withrespect to the executable instruction representations or boxes describedand shown herein, it should be understood that part or all of theexecutable instructions and/or electronic circuits included within onebox may be included in a different box shown in the figures or in adifferent box not shown.

Memory resource 210 may be any electronic, magnetic, optical, or otherphysical storage device that stores executable instructions. Thus,memory resource 210 may be, for example, Random Access Memory (RAM), anElectrically-Erasable Programmable Read-Only Memory (EEPROM), a storagedrive, an optical disc, and the like. The executable instructions may be“installed” on the memory resource 210. Memory resource 210 may be aportable, external or remote storage medium, for example, that allows asystem that includes the memory resource 210 to download theinstructions from the portable/external/remote storage medium. In thissituation, the executable instructions may be part of an “installationpackage”. As described herein, memory resource 210 may be encoded withexecutable instructions related to a locking mechanism of a module of adata center.

The memory resource 210 can include instructions 212 that can beexecutable by a processing resource to monitor a differential pressureof a server rack by averaging differential pressures between individualinlets and outlets (e.g., discharge outlets, etc.) for a plurality ofchassis coupled to the server rack. As used herein, a differentialpressure can, for example, include a pressure difference between aninlet or input pressure and an output or discharge pressure. Forexample, a liquid cooling system can include an inlet where liquidcooling resources (e.g., water, etc.) are received from a liquid toliquid heat exchanger or input manifold. In this example, the liquidcooling system can include an outlet where liquid cooling resources areremoved from a chassis to an output manifold. The differential pressurecan be the difference between an absolute value of the liquid pressureat the inlet and an absolute value of the liquid pressure at the outlet.

The memory resource 210 can include instructions 214 that can beexecutable by a processing resource to determine when a failure occursin response to the differential pressure of the server rack being belowa threshold differential pressure. In some examples, the differentialpressure of a server rack can be utilized to determine when a failure ofone or more chassis cooling systems has occurred. For example, adifferential pressure of a server rack above a threshold differentialpressure can indicate that the chassis cooling systems of the serverrack are operating normally (e.g., operating within a manufacturerspecification, etc.). In another example, a differential pressure of theserver rack below a threshold differential pressure can indicate thatone or more chassis cooling systems have failed or are non-functional(e.g., operating outside a manufacturer specification, etc.).

In some examples, each of a plurality of chassis coupled to the serverrack can include a plurality of pressure sensors to determine the inletpressure and the outlet pressure for each of a plurality of chassis. Insome examples, the inlet pressure and outlet pressure for each of theplurality of chassis can be utilized to determine differential pressureof the server rack. For example, the differential pressure for each ofthe plurality of chassis coupled to the server rack can be averaged(e.g., mean, median, average, etc.) to determine an estimateddifferential pressure for the server rack. As used herein, an averagecan, for example, can represent a central value or values from aplurality of values. In other examples, an inlet pressure and outletpressure of a liquid to liquid heat exchanger can be utilized todetermine a differential pressure for the server rack.

The memory resource 210 can include instructions 216 that can beexecutable by a processing resource to identify a first chassis coupledto the server rack as a failed chassis based on the differentialpressure between the inlet and the discharge of the first chassis. Insome examples, a determination that the differential pressure of theserver rack is below a threshold differential pressure can initiate adetermination of each inlet pressure and outlet pressure for each of theplurality of server chassis coupled to the server rack to identify achassis cooling system that has failed or is non-functional. In someexamples, the inlet pressure and outlet pressure for each chassis can bedetermined based on measured sensor values as described herein. In someexamples, the inlet pressure and outlet pressure for each chassis can beutilized to determine a differential pressure for each chassis. Thedifferential pressure for the first chassis can be below a thresholddifferential pressure and be an indication that the cooling system forthe first chassis is non-functional or failed.

The memory resource 210 can include instructions 218 that can beexecutable by a processing resource to alter settings of a secondchassis to provide additional cooling resources to the first chassis inresponse to identifying the first chassis as a failed chassis. Asdescribed herein, a cooling system of the first chassis can beindependent of a cooling system of the second chassis during normaloperation. As used herein, the term independent, can for example, beutilized to describe devices or systems that may not utilize resourcesof other systems. That is, the cooling system of the first chassis canoperate to a manufacturer specification even when the cooling system ofthe second chassis is non-functional or failed. For example, a serverrack can include a first cooling system of a first chassis that includesa first pump to provide cooling resources (e.g., liquid, etc.) to thefirst cooling system from an input manifold. In addition, the serverrack can include a second cooling system of a second chassis thatincludes a second pump to provide cooling resources to the secondcooling system from the input manifold. In this example, the first pumpcan become non-functional or fail (e.g., lose power, etc.). In thisexample, a failure of the first pump may not affect the functionality ofthe second pump or the second cooling system of the second chassis.

In some examples, the altered settings can include settings that candirect cooling resources originally designated for the second chassis tothe first chassis. For example, the second chassis can include a pumpthat is designated to circulate cooling resources within a coolingsystem of the second chassis. In this example, the settings of the pumpof the second chassis can be altered to also provide cooling resourcesto the first chassis. In some examples, the first chassis and the secondchassis can be connected by an auxiliary input manifold. In someexamples, the altered settings can include utilizing the auxiliary inputmanifold. For example, when a failure is detected at the first chassis,the auxiliary input manifold can be utilized between the first chassisand the second chassis to allow the pump from the second chassis toprovide cooling resources to the first chassis via the auxiliary inputmanifold.

In some examples, the altered settings can include altering settings toincrease a pump speed of a chassis pump of the second chassis to providecooling resources for the first chassis and the second chassis. Asdescribed herein, the pump (e.g., chassis pump) for the second chassiscan be originally designated to circulate cooling resources for thesecond chassis. Thus, the settings of the pump for the second chassismay be altered (e.g., increased pump speed, etc.) so that the pump forthe second chassis can provide cooling resources for both the firstchassis and the second chassis. In some examples, additional pumps forthe second chassis can be activated when a failure is detected at thefirst chassis. For example, the second chassis can include a first pumpand a second pump. In this example, the first pump can be activated andthe second pump can be deactivated during normal operation. In thisexample, settings of the second pump can be altered to activate thesecond pump when a failure is detected at the first chassis such thatthe second pump can provide cooling resources to the first chassis. Inthese examples, the first pump and the second pump can be coupled to thesecond chassis as described herein.

In some examples, the number of altered settings can include settings tobe altered when it is determined that the first chassis is no longernon-functional or is functioning normally. For example, it can bedetermined that power was restored to the first chassis or that thecontroller of the first chassis is operating normally. In some examples,the settings can include settings to stop providing cooling resources tothe first chassis when it is determined that the failure is no longeroccurring at the first chassis. In some examples, the auxiliary inputmanifold can be deactivated or not utilized between the first chassisand the second chassis. In some examples, the pump speed of the chassispump for the second chassis can be lowered to circulate coolingresources within the second chassis and not the first chassis.

The memory resource 210 can be utilized within the second chassis andalter settings of the first chassis when a failure of the first chassisoccurs. In other examples, the memory resource 210 can be a centralresource that can be utilized to perform functions relating to theserver rack. The memory resource 210 can provide additional failover andredundancy for a server rack that includes a plurality of chassis.

FIG. 3 illustrates an example system 320 for a chassis cooling resourceconsistent with the present disclosure. In some examples, a coolingsystem of the first chassis 326-1 can be separated from the coolingsystem of the second chassis 326-2. For example, the cooling system ofthe first chassis 326-1 can include a first pump 358-1, a first inlet352-1, a first discharge outlet 350-1, a first fluid path, and/or afirst liquid reserve to provide cooling resources to the first chassis326-1. In some examples, the first pump 358-1 can include one or morepumps. For examples, the first pump 358-1 can be a plurality of pumpsthat service the first chassis 326-1. In this example, the coolingsystem of the second chassis 326-2 can include a second pump 358-2, asecond inlet 352-2, a second discharge outlet 350-2, a second fluidpath, and/or a second liquid reserve to provide cooling resources to thesecond chassis 326-2.

In some examples, the system 340 can include a first chassis controller300-1 (e.g., controller 100 as referenced in FIG. 1, memory resource 210as referenced in FIG. 2, controller 300-1, 300-2 as referenced in FIG.3, etc.) coupled to a first chassis 326-1 to control functions of afirst pump 358-1 and a first cooling system coupled to the first chassis326-1, wherein the first pump 358-1 receives cooling resources from aliquid to liquid heat exchanger 346 coupled to a third chassis via aninput manifold 342. The third chassis that includes the liquid to liquidheat exchanger 346 is not a server chassis that includes computingdevices such as server blades, but is a position on the server rackwhere a server chassis could be positioned, but is replaced with theliquid to liquid heat exchanger 346.

In some examples, the system 340 can include a second chassis controller300-2 coupled to a second chassis 326-2 to control functions of a secondpump 358-2 and a second cooling system coupled to the second chassis326-2, wherein the second pump 358-2 receives cooling resources from theliquid to liquid heat exchanger 346 coupled to the third chassis via theinput manifold 342. In some examples, the second chassis controller300-2 can determine that the first chassis controller 300-1 has failed.In these examples, the second chassis controller 300-2 can take overcontrol of the first chassis 326-1 to control functions of the firstpump 358-1 and the first cooling system coupled to the first chassis326-1.

In some examples, the system 340 can include an output manifold 344 toreceive cooling resources from the liquid cooling system of the firstserver chassis 326-1 and cooling resources from the liquid coolingsystem of the second server chassis 326-2. As used herein, a liquidcooling system can, for example, refer to a liquid pathway within achassis or server blade, an inlet, a pump, and/or an outlet as describedherein.

In some examples, the system 340 can include an input manifold 342 toprovide cooling resources to the first pump 358-1 at the first serverchassis 326-1 and to provide cooling resources to the second pump 358-2at the second server chassis 326-2. In some examples, the input manifold342 can be positioned between the liquid to liquid heat exchanger 346and the chassis pumps 358-1, 358-2. That is, the liquid to liquid heatexchanger 346 can provide liquid to the first pump 358-1 coupled to thefirst server chassis 326-1 and provide liquid to the second pump 358-2coupled to the second server chassis 326-2.

In some examples, the system 340 can include a first pump 358-1 that iselectrically coupled to a first power supply (e.g., power distributionunit, etc.) that provides electrical power to the first server chassis326-1 and a second pump 358-2 that is electrically coupled to a secondpower supply that provides electrical power to the second server chassis326-2. As described herein, each of the plurality of server chassis326-1, 326-2 can be coupled to a different connection of a power supplyor power distribution unit. In some examples, the first pump 358-1 andthe second pump 358-2 can be electrically coupled to an auxiliary powersupply. In some examples, the auxiliary power supply can include anelectrical connection between the first chassis 326-1 and the secondchassis 326-2, such that power can be provided to the first chassis326-1 by the second chassis 326-2 and vice versa.

FIG. 4 illustrates an example system 440 for a chassis cooling resourceconsistent with the present disclosure. FIG. 4 illustrates an exampleschematic representation illustrated on the left side of FIG. 4 and anexample image representation illustrated on the right side of FIG. 4. Insome examples, the schematic representation on the left can be aschematic of the image representation on the right. In some examples,the system 440 can illustrate an example server that includes a firstchassis 426-1 and a second chassis 426-2. As described herein, the firstchassis 426-1 can be physically separated, communicatively separated,and/or electrically separated from the second chassis 426-2.

In some examples, a cooling system of the first chassis 426-1 can beseparated from the cooling system of the second chassis 426-2. Forexample, the cooling system of the first chassis 426-1 can include afirst pump 458-1, a first inlet 452-1, a first discharge outlet 450-1, afirst fluid path, and/or a first liquid reserve to provide coolingresources to the first chassis 426-1. In some examples, the first pump458-1 can include one or more pumps. For examples, the first pump 458-1can be a plurality of pumps that service the first chassis 426-1. Inthis example, the cooling system of the second chassis 426-2 can includea second pump 458-2, a second inlet 452-2, a second discharge outlet450-2, a second fluid path, and/or a second liquid reserve to providecooling resources to the second chassis 426-2.

In some examples, the system 440 can include a first chassis controller(e.g., controller 100 as referenced in FIG. 1, memory resource 210 asreferenced in FIG. 2, controller 300-1, 300-2 as referenced in FIG. 3,etc.) coupled to a first chassis 426-1 to control functions of a firstpump 458-1 and a first cooling system coupled to the first chassis426-1, wherein the first pump 458-1 receives cooling resources from aliquid to liquid heat exchanger 446 coupled to a third chassis via aninput manifold 442.

In some examples, the system 440 can include a second chassis controllercoupled to a second chassis 426-2 to control functions of a second pump458-2 and a second cooling system coupled to the second chassis 426-2,wherein the second pump 458-2 receives cooling resources from the liquidto liquid heat exchanger 446 coupled to the third chassis via the inputmanifold 442.

In some examples, the system 440 can include an output manifold 444 toreceive cooling resources from the liquid cooling system of the firstserver chassis 426-1 and cooling resources from the liquid coolingsystem of the second server chassis 426-2. As used herein, a liquidcooling system can, for example, refer to a liquid pathway within achassis or server blade, an inlet, a pump, and/or an outlet as describedherein.

In some examples, the system 440 can include an input manifold 442 toprovide cooling resources to the first pump 458-1 at the first serverchassis 426-1 and to provide cooling resources to the second pump 458-2at the second server chassis 426-2. In some examples, the input manifold442 can be positioned between the liquid to liquid heat exchanger 446and the chassis pumps 458-1, 458-2. That is, the liquid to liquid heatexchanger 446 can provide liquid to the first pump 458-1 coupled to thefirst server chassis 426-1 and provide liquid to the second pump 458-2coupled to the second server chassis 426-2.

In some examples, the system 440 can include a first pump 458-1 that iselectrically coupled to a first power supply (e.g., power distributionunit, etc.) that provides electrical power to the first server chassis426-1 and a second pump 458-2 that is electrically coupled to a secondpower supply that provides electrical power to the second server chassis426-2. As described herein, each of the plurality of server chassis426-1, 426-2 can be coupled to a different connection of a power supplyor power distribution unit. In some examples, the first pump 458-1 andthe second pump 458-2 can be electrically coupled to an auxiliary powersupply. In some examples, the auxiliary power supply can include anelectrical connection between the first chassis 426-1 and the secondchassis 426-2, such that power can be provided to the first chassis426-1 by the second chassis 426-2 and vice versa.

In some examples, the system 440 can include an auxiliary input manifold448. In some examples, the auxiliary input manifold 448 can be separatefrom the input manifold 442. In some examples, the input manifold 442can be coupled to each of the plurality of chassis 426-1, 426-2 via aparallel connection. For example, the input manifold 442 can include apathway with a plurality of outputs to couple to corresponding inlets.In this way each inlet of the plurality of chassis 426-1, 426-2 arecoupled directly to the liquid to liquid heat exchanger 446. In someexamples, the liquid to liquid heat exchanger 446 can be coupled to aserver chassis location (e.g., a position of the server rack that canreceive a server chassis, etc.) to provide cooling resources to thefirst pump 458-1 coupled to the first liquid cooling system of the firstchassis 426-1 and to the second pump 458-2 coupled to the second liquidcooling system of the second chassis 426-2.

In some examples, the auxiliary input manifold 448-1, 448-2 can becoupled to the plurality of chassis 426-1, 426-2. For example, the firstchassis 426-1 can be coupled to the auxiliary input manifold 448-1 at anauxiliary input 454-1. In this example, the auxiliary input manifold448-1 can be coupled to an auxiliary output of a different chassis. Inthis example, the auxiliary input manifold 448-2 can be coupled to anauxiliary output 456-1 of the first chassis 426-1 and an auxiliary input454-2 of the second chassis 426-2. In some examples, the second chassis426-2 can also include an auxiliary output 456-2 that can be utilized tocouple the second chassis 426-2 to an auxiliary input of a differentchassis. Said another way, the auxiliary input manifold 448 can becoupled to the auxiliary output 456-1 of the first liquid cooling systemof the first chassis 426-1 and the auxiliary input 454-2 of the secondliquid cooling system of the second chassis 426-2. In some examples, theauxiliary input manifold 448-1, 448-2 can create a parallel pathway forthe chassis pumps 458-1, 458-2 to share across a plurality of chassis426-1, 426-2. In some examples, every chassis can linked by a highpressure side that utilizes the pumps 458-1, 458-2 in order to create ashared system to improve reliability and resiliency in the event one ormore of the pumps 458-1, 458-2 in the system 440 are not functioning.

In some examples, the system 440 can include a first pump 458-1 coupledto a first server chassis 426-1 and a liquid cooling system of the firstserver chassis 426-1. In some examples, the system 440 can include afirst chassis pump 458-1 coupled to the first chassis 426-1 and a secondchassis pump 458-2 coupled to the second chassis 426-2. In someexamples, the first chassis pump 458-1 can be separate from the secondchassis pump 458-2. For example, during normal operation, the firstchassis pump 458-1 can provide cooling resources or circulate coolingresources for a first cooling system of the first chassis 426-1 withoutproviding cooling resources to a cooling system of the second chassis426-2. In a similar way, during normal operation, the second chassispump 458-2 can provide cooling resources for a second cooling system ofthe second chassis 426-2 without providing cooling resources to acooling system of the first chassis 426-1. In some examples a normaloperation can be a first state or active state. In some examples, afailure can be a second state or inactive state. Thus, in some examples,first pump 458-1 may provide cooling resources to the first liquidcooling system of the first chassis 426-1 during a first state of thesystem. In addition, the first pump 458-1 may provide cooling resourcesto the first liquid cooling system of the first chassis 426-1 and to thesecond liquid cooling system of the second chassis 426-2 during a secondstate of the system. In some examples, the first server chassis 426-1can be online during the first state of the system and the second serverchassis 426-2 can be offline during the second state of the system.

In some examples, a first controller of the first chassis 426-1 can beutilized to control functions of a first cooling system of the firstchassis 426-1 and a second controller of the second chassis 426-2 can beutilized to control functions of a second cooling system of the secondchassis 426-2. For example, the first controller of the first chassis426-1 can be utilized to control a pump speed of the chassis pump 458-1coupled to the first chassis 426-1. In another example, the secondcontroller of the second chassis 426-2 can be utilized to control a pumpspeed of the chassis pump 458-2 coupled to the second chassis 426-2. Insome examples, the first controller can alter settings of the chassispump 458-1 based on operation conditions of the first chassis 426-1.

For example, the first chassis 426-1 may be running at a relatively highcapacity. In this example, the first controller of the first chassis426-1 can alter the pump speed to an increased pump speed to ensurecomponents are operating at a particular temperature during therelatively high capacity. In this example, the second controller of thesecond chassis 426-2 can alter a pump speed of the pump 458-2 based onoperation conditions of the second chassis 426-2 independent of thefirst chassis 426-1. In this way, each chassis can be independentlycontrolled by a corresponding controller based on an operation conditionof the chassis. As used herein, operation condition can, for example,include a performance level that corresponds to heat generation ofcomponents. In some examples, a speed of the pump 458-1 can be based ona power level of the plurality of servers within the first serverchassis 426-1. For example, a controller of the first chassis 426-1 candetermine a power level being drawn by the plurality of servers coupledto the first chassis 426-1. In this example, the pump speed of the pump458-1 can be altered based on the determined power level. In someexamples, the pump speed of the pump 458-2 can be altered based on thedetermined power level of the second chassis 426-2 and the first chassis426-1 when there is a failure associated with the first chassis 426-1and the second chassis 426-2 is providing additional cooling resourcesto the first chassis 426-1.

In some examples, the second controller of the second chassis 426-2 candetermine that a failure has occurred at the first chassis 426-1. Forexample, the second controller can determine that the chassis pump 458-1has failed. In this example, the second controller can alter a settingsof the chassis pump 458-2 to provide additional cooling resources to thefirst chassis 426-1 and/or cooling system of the first chassis 426-1. Inthis example, the second controller can utilize the auxiliary inputmanifold 448-1 to connect the cooling system of the first chassis 426-1to the cooling system of the second chassis 426-2. That is, the secondpump 458-2 can provide cooling resources to the liquid cooling system ofthe first chassis 426-1 when the first chassis 426-1 is deactivated. Inthis way, the chassis pump 458-2 can provide cooling resources to boththe second chassis 426-2 and the first chassis 426-1 via the auxiliaryinput manifold 448-1 and the increased pump speed of the pump 458-2. Inthis way, the system 440 can provide cooling resource redundancy betweenthe chassis 426-1, 426-2 and also provide cooling resources for eachchassis based on operation conditions of the chassis 426-1, 426-2.

In some examples, the auxiliary input manifold 448-1 can be a secondinput manifold that equalizes a pressure of the first liquid coolingsystem of the first chassis 426-1 and the second liquid cooling systemof the second chassis 426-2. For example, pressure drops or increasescan occur when a cooling system fails and is supplemented with coolingresources from a different cooling system. In some examples, coolingresources are directed from the first liquid cooling system of the firstchassis 426-1 to the second liquid cooling system of the second chassis426-2 when the second pump 458-2 fails. For example, a liquid reservefrom the first cooling system of the first chassis 426-1 can be utilizedfor the second liquid cooling system of the second chassis 426-2 whenthe second pump 458-2 fails or becomes non-functional (e.g., losespower, mechanical failure, etc.).

FIG. 5 illustrates an example system 520 for a chassis cooling resourceconsistent with the present disclosure. System 520 can include a serverrack that includes a plurality of chassis 526-1, 526-2 (e.g., serverchassis, etc.). As described herein, a chassis 526-1, 526-2 can includea plurality of server blades that each include computing devices. Insome examples, a first chassis 526-1 can be independent from a secondchassis 526-2. For example, the first chassis 526-1 can performfunctions that are independent from the functions performed by thesecond chassis 526-2.

In some examples, the cooling system for the first chassis 526-1 can beindependent from the cooling system for the second chassis 526-2. Insome examples, the first chassis 526-1 can include a first controller500-1 (e.g., controller 100 as referenced in FIG. 1, memory resource 210as referenced in FIG. 2, etc.) and the second chassis 526-2 can includea second controller 500-2 (e.g., controller 100 as referenced in FIG. 1,memory resource 210 as referenced in FIG. 2, etc.).

In some examples, the system 520 can include a first chassis controller500-1 coupled to a first chassis 526-1 to control functions of a firstpump and a first cooling system coupled to the first chassis 526-1,wherein the first pump receives cooling resources from a liquid toliquid heat exchanger coupled to a third chassis via an input manifold.In some examples, the first chassis controller 500-1 can be independentfrom the second chassis controller 500-2 when the first chassis 526-1and the second chassis 526-2 are functioning normally (e.g., functioningwithin manufacturer specifications, etc.). For example, the firstchassis controller 500-1 can be restricted from performing functionsdesignated to the second chassis controller 500-2 when the first chassis526-1 and the second chassis 526-2 are functioning normally.

In addition, the first pump coupled to the first chassis can beindependent from a second pump coupled to the second chassis 526-2. Forexample, the first pump can provide cooling resources to the firstcooling system of the first chassis 526-1 without affecting or beingeffected by the second pump coupled to the second chassis 526-2. Duringnormal operation (e.g., when a failure does not exist, when a system isoperating within manufacturer specifications, etc.) the first pump cancirculate cooling resources to a first cooling system of the firstchassis 526-1 and the second pump can circulate cooling resources to asecond cooling system of the second chassis 526-2.

In some examples, the system 520 can include a second chassis controller500-2 coupled to a second chassis 526-2 to control functions of a secondpump and a second cooling system coupled to the second chassis 526-2,wherein the second pump receives cooling resources from the liquid toliquid heat exchanger coupled to the third chassis via the inputmanifold. In some examples, the first chassis 526-2 and the secondchassis 526-2 can be physically separated from the liquid to liquid heatexchanger. For example, the first chassis 526-1 can include a firstenclosure and the second chassis 526-2 can include a second enclosurethat is separate from the first chassis 526-1.

In some examples, the first chassis 526-1 and the second chassis 526-2can be electrically separated. For example, the first chassis 526-1 canbe coupled to a first power distribution unit 522-1 via a firstconnection 524-1. In this example, the second chassis 526-2 can becoupled to the first power distribution unit 522-1 via a secondconnection 528-1. In some examples, the first power distribution unit522-1 can include a plurality of connections (e.g., connections 528-1,524-1, etc.). In some examples, each connection of the first powerdistribution unit 522-1 can be electrically independent. As used herein,electrically independent can, for example, include providing electricalpower to a first load via first connection without affecting a secondload connected to a second connection. In this way, power can beprovided to connection 528-1 even if connection 524-1 fails.

In some examples, the system 520 can include a second power distributionunit 522-2. The second power distribution unit 522-2 can be coupled tothe first chassis 526-1 via a connection 524-2 and coupled to the secondchassis 526-2 via connection 528-2. In some examples, the second powerdistribution unit 522-2 can provide electrical power to the firstchassis 526-1 and/or to the second chassis 526-2 when the first powerdistribution unit 522-2 fails.

In some examples, the system 520 can include an auxiliary connection530-1 that can electrically couple and/or communicatively couple thefirst chassis 526-1 to the second chassis 526-2. In some examples, theauxiliary connection 530-1 can be utilized by the controller 500-2coupled to the second chassis 526-2 to alter settings of a coolingsystem of the first chassis 526-1. For example, the auxiliary connection530-1 can be a communication link between a controller 500-1 of thefirst chassis 526-1 and a controller 500-2 of the second chassis 526-2.In some examples, the auxiliary connection 530-1 can be a wired orwireless connection between the first chassis 526-1 and the secondchassis 526-2 to allow the controller 500-2 of the second chassis 526-2to alter settings of the first chassis 526-1 when a failure is detectedat the first chassis 526-1. For example, the controller 500-2 of thesecond chassis 526-2 can utilize the auxiliary connection 530-1 toprovide power to a pump coupled to the first chassis 526-1, altersettings of the pump coupled to the first chassis 526-1, and/or altersettings of the controller 500-1 of the first chassis 526-1. In someexamples, the system 520 can include additional auxiliary cables (e.g.,auxiliary cable 530-2, etc.) to couple the second chassis 526-2 toadditional server chassis coupled to the server rack.

In some examples, the auxiliary connection 530-1 can be activated anddeactivated in response to a detected failure. For example, theauxiliary connection 530-1 can be deactivated when the first chassis526-1 and the second chassis 526-2 are functioning normally. In anotherexample, the auxiliary connection 530-1 can be activated when a failureis detected at the first chassis 526-1 or the second chassis 526-2. Inthis way, the system 520 allows for each chassis 526-1, 526-2 tofunction independent of the other chassis coupled to the server rackuntil there is a failure.

In the foregoing detailed description of the present disclosure,reference is made to the accompanying drawings that form a part hereof,and in which is shown by way of illustration how examples of thedisclosure may be practiced. These examples are described in sufficientdetail to enable those of ordinary skill in the art to practice theexamples of this disclosure, and it is to be understood that otherexamples may be utilized and that process, electrical, and/or structuralchanges may be made without departing from the scope of the presentdisclosure.

The figures herein follow a numbering convention in which the firstdigit corresponds to the drawing figure number and the remaining digitsidentify an element or component in the drawing. Elements shown in thevarious figures herein can be added, exchanged, and/or eliminated so asto provide a number of additional examples of the present disclosure. Inaddition, the proportion and the relative scale of the elements providedin the figures are intended to illustrate the examples of the presentdisclosure, and should not be taken in a limiting sense. As used herein,the designator “N”, particularly with respect to reference numerals inthe drawings, indicates that a number of the particular feature sodesignated can be included with examples of the present disclosure. Thedesignators can represent the same or different numbers of theparticular features. Further, as used herein, “a number of” an elementand/or feature can refer to one or more of such elements and/orfeatures.

What is claimed:
 1. A system, comprising: a first chassis controller tocontrol functions of a first pump and a first cooling system of a firstchassis coupled to a server rack, wherein the first pump receivescooling resources from a liquid to liquid heat exchanger coupled to athird chassis via an input manifold and provides the received coolingresources to the first cooling system; and a second chassis controllerto control functions of a second pump and a second cooling system of asecond chassis coupled to the server rack, wherein the second pumpreceives cooling resources from the liquid to liquid heat exchanger viathe input manifold and provides the received cooling resources to thesecond cooling system; wherein a high pressure side of the first coolingsystem is connected to-a high pressure side of the second cooling systemvia an auxiliary manifold such that: the first pump can provide coolingresources to the second cooling system via the auxiliary manifold if thesecond pump fails, and the second pump can provide cooling resources tothe first cooling system via the auxiliary manifold if the second firstpump fails.
 2. The system of claim 1, wherein the second chassiscontroller includes instructions to: determine a failure of the firstchassis controller; and control functions of the first pump and thefirst cooling system of the first chassis.
 3. The system of claim 1,wherein the liquid to liquid heat exchanger is separated from the firstchassis.
 4. The system of claim 1, wherein the first controllercomprises instructions to detect a failure of the second pump and, inresponse, increase a speed of the first pump, and wherein the secondcontroller comprises instructions to detect a failure of the first pumpand, in response, increase a speed of the second pump.